Dialog system

A dialog system or conversational agent (CA) is a computer system intended to converse with a human, with a coherent structure. Dialog systems have employed text, speech, graphics, haptics, gestures and other modes for communication on both the input and output channel.

What does and does not constitute a dialog system may be debatable. The typical GUI wizard does engage in some sort of dialog, but it includes very few of the common dialog system components, and dialog state is trivial.

Contents 1 Components 1.1 Dialog manager 2 Types of systems 3 Applications 4 Toolkits and architectures 5 References 6 Further reading 7 External links

Components

There are many different architectures for dialog systems. What sets of components are included in a dialog system, and how those components divide up responsibilities differs from system to system. Principal to any dialog system is the dialog manager, which is a component that manages the state of the dialog, and dialog strategy. A typical activity cycle in a dialog system contains the following phases^[1]:

1. The user speaks, and the input is converted to plain text by the system's input recognizer/decoder, which may include:
   • automatic speech recognizer (ASR)
   • gesture recognizer
   • handwriting recognizer
2. The text is analyzed by a Natural language understanding unit (NLU), which may include:
   • Proper Name identification
   • part of speech tagging
   • Syntactic/semantic parser
3. The semantic information is analyzed by the dialog manager (see section below), along with a task manager that has knowledge of the specific task domain.
4. The dialog manager produces output using an output generator, which may include:
   • natural language generator
   • gesture generator
   • layout engine
5. Finally, the output is rendered using an output renderer, which may include:
   • text-to-speech engine (TTS)
   • talking head
   • robot or avatar

Dialog systems that are based on a text-only interface (e.g. text-based chat) contain only stages 2-4.

Dialog manager

The dialog manager is the core component of the dialog system. It maintains the history of the dialog, adopts certain dialog strategy (see below), retrieve the content (stored in files or databases), and decides on the best response to the user. The dialog manager maintains the dialog flow.

The design of the dialog manager evolves over time.

• finite-state machine
• frame-based: The system has several slots to be filled. The slots can be filled in any order. This supports mixed-initiative dialog strategy.
• information-state based

The dialog flow can have the following strategies:

• System-initiative dialog: The system is in control to guide the dialog at each step.
• Mixed-initiative dialog: Users can barge in and change the dialog direction. The system follows the user request, but tries to direct the user back the original course. This is the most commonly used dialog strategy in today's dialog systems.
• User-initiative dialog: The user takes lead, and the system respond to whatever the user directs.
• Learned strategy: the system's next dialogue action is chosen based on an optimisation method such as Reinforcement Learning

The dialog manager can be connected with an expert system to give the ability to respond with specific expertise.

Types of systems

Dialog systems fall into the following categories, which are listed here along a few dimensions. Many of the categories overlap and the distinctions may not be well established.

• by modality
  • text-based
  • spoken dialog system
  • graphical user interface
  • multi-modal
• by device
  • telephone-based systems
  • PDA systems
  • in-car systems
  • robot systems
  • desktop/laptop systems
    • native
    • in-browser systems
    • in-virtual machine
  • in-virtual environment
  • robots
• by style
  • command-based
  • menu-driven
  • natural language
  • speech graffiti
• by initiative ^[2]
  • system initiative
  • user initiative
  • mixed initiative

Applications

Dialog systems can support a broad range of applications in business enterprises, education, government, healthcare, and entertainment.^[3] For example:

• Responding to customers' questions about products and services via a company’s website or intranet portal
• Customer service agent knowledge base: Allows agents to type in a customer’s question and guide them with a response
• Guided selling: Facilitating transactions by providing answers and guidance in the sales process, particularly for complex products being sold to novice customers
• Help desk: Responding to internal employee questions, e.g., responding to HR questions
• Website navigation: Guiding customers to relevant portions of complex websites --a Website concierge
• Technical support: Responding to technical problems, such as diagnosing a problem with a product or device
• Personalized service: Conversational agents can leverage internal and external databases to personalize interactions, such as answering questions about account balances, providing portfolio information, delivering frequent flier or membership information, for example
• Training or education: They can provide problem-solving advice while the user learns
• Simple dialog systems are widely used to decrease human workload in call centres. In this and other industrial telephony applications, the functionality provided by dialog systems is known as interactive voice response or IVR.

In some cases, conversational agents can interact with users using artificial characters. These agents are then referred to as embodied agents.

Toolkits and architectures

A survey of current frameworks, languages and technologies for defining dialog systems.

Name & Links	System Type	Description	Affiliation[s]	Environment[s]	Comments
AIML	Chatterbot language	XML dialect for creating natural language software agents	Richard Wallace
CSLU Toolkit		a state-based speech interface prototyping environment	OGI School of Science and Engineering M. McTear Ron Cole		publications are from 1999.
VXML Voice XML	Spoken dialog	multimodal dialog markup language	developed initially by AT&T then administered by an industry consortium and finally a W3C specification	Example	primarily for telephony.
SALT	markup language	multimodal dialog markup language	Microsoft		"has not reached the level of maturity of VoiceXML in the standards process".
Quack.com - QXML	Development Environment		company bought by AOL

References

1. ^ Jufarsky & Martin (2009), Speech and language processing. Pearson International Edition, ISBN 978-0-13-504196-3, Chapter 24
2. ^ Will, Thomas (2007). Creating a Dynamic Speech Dialogue. VDM Verlag Dr. Müller. ISBN 978-3836449908. 
3. ^ Lester, J.; Branting, K.; Mott, B. (2004), "Conversational Agents", The Practical Handbook of Internet Computing, Chapman & Hall, http://www.astutesolutions.com/downloads/conversational_agents_Lester_RealDialog.pdf 

Further reading

• Will, Thomas (2007). Creating a Dynamic Speech Dialogue. VDM Verlag Dr. Müller. ISBN 978-3836449908. 

External links

• The Conversational Interface: Our Next Great Leap Forward, 2003, article on the CI by futurist John Smart.
• Dialogue Processing in Spoken Language Systems
• Voice User Interface Design
• Spoken Dialogue Technology: Towards the Conversational Interface
• Machine Conversations
• Dialog system at BookRags.
• Dialogue system links by Staffan Larsson.
• Machine learning approaches to building spoken dialogue systems: the CLASSiC project.